- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.4k
Upgrade freetype port from 2.6 to 2.13.3 #22585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| ****** ***** | ||
| +****+ +**** | ||
| +****+ +**** | ||
| **** **** | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the rendering is slightly thinner with the new version.. do you think this kind of change is normal/acceptable when upgrading freetype.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's intentional on the FT side, I assume.
a353343    to
    b668457      
    Compare
  
    b668457    to
    078e330      
    Compare
  
    | ****** ***** | ||
| +****+ +**** | ||
| +****+ +**** | ||
| **** **** | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's intentional on the FT side, I assume.
078e330    to
    50062a6      
    Compare
  
    3fd8daa    to
    e2e298d      
    Compare
  
    | reftests updated. PTAL. | 
e2e298d    to
    4f7b0e8      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
Also, switch from a fork to using the upstream github repo. We had a single patch in our fork: emscripten-ports/FreeType@40a760c However, this was upstreamed in: freetype/freetype@2f4b740 This change is based on emscripten-core#18088. Fixes: emscripten-core#22571
4f7b0e8    to
    def27ab      
    Compare
  
    | This seems to be failing on the Chromium Windows bot: https://ci.chromium.org/ui/p/emscripten-releases/builders/try/win/b8736319351635088817/overview I haven't tried to repro locally, but let me know if you need me to; i do have a windows cloudtop. | 
| 
 Thanks, I'll take a look. | 
The subprocess creation on windows really doesn't like it when an argument contains < or >. Instead of trying to defined `FT_CONFIG_CONFIG_H` or point to our own version, just overwrite the default version. See emscripten-core#22585 (comment)
The subprocess creation on windows really doesn't like it when an argument contains < or >. Instead of trying to defined `FT_CONFIG_CONFIG_H` or point to our own version, just overwrite the default version. See emscripten-core#22585 (comment)
The subprocess creation on windows really doesn't like it when an argument contains < or >. Instead use the default `FT_CONFIG_CONFT_CONFIG_CONFIG_H` and define the two `HAVE_` macros on the command line. See #22585 (comment) --------- Co-authored-by: Derek Schuff <[email protected]>
Also, switch from a fork to using the upstream github repo. We had a single patch in our fork:
emscripten-ports/FreeType@40a760c
However, this was upstreamed in:
freetype/freetype@2f4b740
This change is based on #18088.
Fixes: #22571